View MVI56-DH485_2683899.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

MVI56-DH485 controllogix platform dh485 interface module user manual november 12, 2004
page 2 of 85 prosoft technology, inc. november 12, 2004 please read this notice successful application of this module requires a reasonable working knowledge of the controllogix platform dh485 interface module hardware and the applic ation in which the combination is to be used. for this reason, it is important that those responsible for implement ation satisfy themselves that the combination will meet the needs of the application without exposing personnel or equipment to unsafe or inappropriate working conditions. this manual is provided to assist the user. every attempt has been made to assure that the information provided is accurate and a true reflection of the pro duct's installation requirements. in order to assure a complete understanding of the operation of the pr oduct, the user should read all applicable allen- bradley documentation on the oper ation of the a-b hardware. under no conditions will prosoft technology, inc. be re sponsible or liable for indirect or consequential damages resulting from the use or application of the product. reproduction of the contents of this manual, in whole or in part, without written permission from prosoft technology, inc. is prohibited. information in this manual is subject to change without notice and does not represent a commitment on the part of prosoft technology, inc. improvements and/or changes in this manual or the product may be made at any time. these changes will be made periodically to correct technical inaccuracies or typographical errors. prosoft technology, inc. 1675 chester avenue, 2 nd floor bakersfield, ca 93301 (661) 716-5100 (661) 716-5101 (fax) www.prosoft-technology.com copyright ? prosoft technology, inc. 2000 ? 2004. all rights reserved. MVI56-DH485 user manual november 12, 2004
table of contents MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 3 of 85 november 12, 2004 table of contents please read th is notice ........................................................................................................ .. 2 1 introduction ................................................................................................................... ...... 5 1.1 general co ncepts........................................................................................................... 5 1.2 verifying the ju mper settings ...................................................................................... 5 2 understanding the architec ture ............................................................................... 7 2.1 main logic loop ............................................................................................................. 7 2.2 controllogix processor not in run ............................................................................. 7 2.3 backplane data transfer ............................................................................................... 8 2.3.1 normal data transfer ................................................................................................... 9 2.3.2 command contro l blocks ........................................................................................... 11 2.4 master dr iver................................................................................................................. 1 4 2.5 slave dr iver................................................................................................................... 15 2.6 cif da ta ....................................................................................................................... .. 17 2.7 slc interf ace ................................................................................................................ 19 2.7.1 slc communicati on set up....................................................................................... 20 2.7.2 ladder lo gic ............................................................................................................... 21 3 module configuration ................................................................................................... 27 3.1 setting up th e module.................................................................................................. 27 3.2 module data object (dh485moduled ef)..................................................................... 31 3.2.2 user data objects....................................................................................................... 33 4 modifying the sample ladder logic ......................................................................... 35 4.1 power up ....................................................................................................................... 35 4.2 mainrout ine .................................................................................................................. 36 4.3 readdata ....................................................................................................................... 37 4.4 writedata...................................................................................................................... .38 5 modifying the conf iguration data ........................................................................... 43 5.1 command list overview.............................................................................................. 44
MVI56-DH485 ? controllogix platform table of contents dh485 interface module page 4 of 85 prosoft technology, inc. november 12, 2004 5.1.1 command entry format ..............................................................................................44 5.2 file override mapping ..................................................................................................46 5.2.1 file override en try form at ..........................................................................................46 6 diagnostics and tr oubleshoo ting ...........................................................................47 6.1 status data from the module?s input image..............................................................47 6.2 configuration/ debug port ............................................................................................47 6.2.1 required ha rdware .....................................................................................................47 6.2.2 required so ftware.......................................................................................................48 6.2.3 using the port..............................................................................................................48 6.2.4 menu opti ons ..............................................................................................................49 6.3 led status i ndicators...................................................................................................55 6.3.1 clearing a faul t condition...........................................................................................56 6.3.2 troublesho oting...........................................................................................................57 7 cable connec tions ...........................................................................................................59 7.1 dh485 communicati on ports ......................................................................................59 7.1.1 connecting the cable to the co nnector ......................................................................59 7.2 rs-232 configurat ion/debug port...............................................................................62 appendix a ? mvi56-dh 485 status data...............................................................................63 appendix b ? mvi56-dh 485 configur ation..........................................................................67 timer, counter, and cont rol data types...................................................................................72 appendix c ? MVI56-DH485 conf iguration file example ..............................................77 appendix d ? produc t specificat ions ...............................................................................81 general speci fications......................................................................................................... .......81 functional sp ecifications ...................................................................................................... .....81 physical....................................................................................................................... ...............81 controllogix interface......................................................................................................... .......82 hardware sp ecifica tions........................................................................................................ .....82 support, service, and warra nty .......................................................................................83
introduction MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 5 of 85 november 12, 2004 1 introduction the MVI56-DH485 (?dh485 communication mo dule?) product allows allen-bradley controllogix i/o compatible processors to easily interface with other dh485 protocol compatible devices. compatible devices include not only allen-bradley plc?s and slc's (which support the dh485 protocol) but also a wide assortment of end devices. the MVI56-DH485 module acts as a gateway between the dh485 network and the allen-bradley backplane. the data transfer from the controllogix processor is asynchronous from the actions on the dh485 network. a 4000-word register space in the module is used to exchange data between the processor and the dh485 network. the module can send and receive commands from other nodes on the dh485 network. each port works as an independent dh485 node. 1.1 general concepts the following discussion covers several concepts that are key to understanding the operation of the MVI56-DH485 module. on power up the module begins performing the following logical functions: 1. initialize hardware components a. initialize controllogix backplane driver b. test and clear all ram c. initialize the serial communication ports 2. reads configuration information from the compact flash disk 3. initialize module register space 4. enable slave driver 5. enable master driver once the module has received the module configuration from the compact flash disk, the module will begin communicating with other nodes on the network, depending on the configuration. 1.2 verifying the jumper settings there are three jumpers located at the bottom of the module.
MVI56-DH485 ? controllogix platform introduction dh485 interface module page 6 of 85 prosoft technology, inc. november 12, 2004 verify that the jumpers on the module match the settings shown in the above illustration. the setup jumper should only be jumped when programming the module or when instructed to do so by prosoft technology, inc. the prt2 and prt3 jumpers are used to configure ports 2 and 3 for rs-232, rs- 422, or rs-485 communications. the default jumper setting for both application ports is rs-232.
understanding the architecture MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 7 of 85 november 12, 2004 2 understanding the architecture this section gives the reader a functional overview of the MVI56-DH485 module. a thorough understanding of the information contained in this document is required for successful implementation of the modul e in a user application. if you already understand the content of this section, refer to the module configuration section to get the module up and running. if you are not familiar with the data transfer operation, read this section before setting up the module. the module is designed to insulate the user from requiring a comprehensive knowledge of the dh485 protocol specification. some knowledge is required when constructing commands and understanding the data types used in the protocol. this information is supplied in this manual where required. 2.1 main logic loop upon completing the power up configuration process, the module enters an infinite loop that performs the functions shown in the following diagram. call i/o handler - transfers data between module and processor (user, status, configuration, etc.) call serial port driver (configuration/debug port) - rx and tx buffer routines are interrupt driven - call to serial port routines checks to see if there is any data in the buffer, and depending on the value will either service the buffer or wait for more characters call i/o handler call cfg/dbg port driver call dh485 driver -handle issuing of commands and servicing requests from other nodes from power up logic call dh485 driver call i/o handler - transfers data between module and processor (user, status, configuration, etc.) call serial port driver (configuration/debug port) - rx and tx buffer routines are interrupt driven - call to serial port routines checks to see if there is any data in the buffer, and depending on the value will either service the buffer or wait for more characters call i/o handler call cfg/dbg port driver call cfg/dbg port driver call dh485 driver -handle issuing of commands and servicing requests from other nodes from power up logic call dh485 driver call dh485 driver 2.2 controllogix processor not in run anytime the module detects that the processor has gone out of the run mode (i.e., fault or pgm), the dh485 ports can be shut down as prescribed in the user configuration. when the processor is returned to a running state, the module will resume communications on the network.
MVI56-DH485 ? controllogix platform understanding the architecture dh485 interface module page 8 of 85 prosoft technology, inc. november 12, 2004 2.3 backplane data transfer the MVI56-DH485 module is unique in the way that the controllogix backplane is utilized. data is paged between the module and the controllogix processor across the backplane using the module?s input and output images. the update frequency of the images is determined by the scheduled scan rate defined by the user for the module and the communication load on the module for the input and output images. typical updates are in the range of 1 to 10 milliseconds. this bi-directional transference of data is accomplished by the module filling in data in the module?s input image to send to the processor. data in the input image is placed in the controller tags in the processor by the ladder logic. the input image for the module is set to 250 words. this large data area permits fast throughput of data between the module and the processor. the processor inserts data in the module?s output image to be transferred to the module. the module?s program extracts the data and places it in the module?s internal database. the output image for the module is set to 248 words. this large data area permits fast throughput of data from the processor to the module. the following diagram displays the data transfer method used to move data between the controllogix processor, the MVI56-DH485 module, and the dh485 network. dh485 port driver master driver logic master driver logic slave driver logic slave driver logic module?s internal database MVI56-DH485 module to dh485 network ladder logic transfers data from module?s input image to data areas in the processor controllogix processor controller tags controllogix processor ladder logic transfers data from processor data areas to output image input image output image backplane driver status read data write data special control blocks as shown in the previous diagram, all data transferred between the module and the processor over the backplane is through the input and output images. ladder logic must be written in the controllogix processor to interface the input and output image
understanding the architecture MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 9 of 85 november 12, 2004 data with data defined in the controller tags. all data used by the module is stored in its internal database. the following diagram shows the layout of the database. 4000 registers for user data register data module?s internal database structure 0 3999 data contained in this database is paged through the input and output images by coordination of the controllogix ladder logic and the MVI56-DH485 module?s program. up to 250 words of data can be transferred from the module to the processor at once. up to 248 words of data can be transferred from the processor to the module. the read and write block identification codes in each data block determine the function to be performed or the content of the data block. the block identification codes used by the module are listed in the following table: block range descriptions 0 or -1 status block 1 to 20 read or write data 1000 to 1019 read data initialization blocks 3000 port 0 command disable block 3001 port 0 command enable block 3002 port 0 command conditional block 3100 port 1 command disable block 3101 port 1 command enable block 3102 port 1 command conditional block 9998 warm-boot control block 9999 cold-boot control block each image has a defined structure depending on the data content and the function of the data transfer as defined in the following sections. 2.3.1 normal data transfer normal data transfer includes the transferring of data received by, or to be transmitted to, the dh485 drivers and the status data. this data is transferred through read (input image) and write (output image) blocks. the section entitled module configuration provides a description of the data objects used with the blocks and the ladder logic required. the following sections discuss the structure and function of each block.
MVI56-DH485 ? controllogix platform understanding the architecture dh485 interface module page 10 of 85 prosoft technology, inc. november 12, 2004 2.3.1.1 read block these blocks of data are used to transfer information from the module to the controllogix processor. the structure of the input image used to transfer this data is shown in the following table: offset description length 0 reserved 1 1 write block id 1 2-201 read data 200 202 program scan counter 1 203-204 product code 2 205-206 product version 2 207-208 operating system 2 209-210 run number 2 211-216 data transfer status 6 217-248 spare 32 249 read block id 1 the data transfer status has the following structure (words 211 to 216): word description 211 block reads 212 block write 213 block parse 214 block events 215 block commands 216 block error the block identification code (word 249) is used to signal to the controllogix processor that a new block is ready for processing and informs the processor of the contents of the block. if the value of the code is set to 1, the block contains the first 200 words of data contained in the database of the module. the block also contains the block identific ation code the module expects to receive from the processor (word 1 in the block). under normal data transfer conditions, the ladder logic should use the code to build the appropriate block for the module in the output image. normal read data blocks also contain status information (words 202 to 216) that can be used to determine the health of the module. the example ladder logic displays how this information is stored in controller tags in the processor. this information is also passed to the processor for block identification codes 0 and ?1 along with the status data for each port. the format of these blocks is as follows:
understanding the architecture MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 11 of 85 november 12, 2004 offset description length 0 reserved 1 1 write block id 1 2-51 port 0 status 50 52-101 port 1 status 50 102-201 reserved 100 202 program scan counter 1 203-204 product code 2 205-206 product version 2 207-208 operating system 2 209-210 run number 2 211-216 data transfer status 6 217-248 reserved 32 249 read block id (0 or -1) 1 refer to appendix a for a detailed listing of the content of this data block. 2.3.1.2 write block these blocks of data are used to transfer information from the controllogix processor to the module. the structure of the output image used to transfer this data is shown in the following table. offset description length 0 write block id 1 1-200 write data 200 201-247 spare 47 the write block id is an index value used to determine the location in the module?s database where the data will be placed. each transfer can move up to 200 words. 2.3.2 command control blocks command control blocks are special blocks used to control the module or perform special operations. the current version of the software supports four different command control blocks: initialize the read data, change command type control, warm boot, and cold boot: 2.3.2.1 initialize the read data important: in order to use this feature, you must change the ?initialize output data? parameter to ?yes? in the configuration file. blocks 1000 to 1019 are used to initialize the read data when the module starts. this is the data passed from the module?s internal database to the processor during normal operation. this optional function can be used to set the read data area to the values last read from the module before the first transfer of data from the module to the processor. the module will request this data from the processor using a block with the following format: offset description length 0 reserved 1 1 1000 to 1019 1 2-248 spare 247 249 1000 to 1019 1
MVI56-DH485 ? controllogix platform understanding the architecture dh485 interface module page 12 of 85 prosoft technology, inc. november 12, 2004 the block number utilized represents the 200-word offset of data requested. therefore, when the module request block 1000, the processor should return the first 200 words of read data. for block 1001, the processor should return the second 200 words of read data. the format of the response block built by the module is as follows: offset description length 0 1000 to 1019 1 1 to 200 data to place in output area 200 201-247 spare 47 the number of blocks requested by the module from the processor is dependent on the number of read registers configured for the module. if the module is configured for 600 registers, 3 blocks (1000 to 1002) will be requested. this data will be placed in the module?s internal database starting at the read register configured for the module. use of this feature requires ladder logic to process the blocks requested. the example ladder logic displays a rung that will handle this optional feature. 2.3.2.2 change command type control block blocks 3000, 3001, 3002, 3100, 3101 and 3102 are used to alter the command type for entries in the user command list. when commands are processed during the startup of the module, the command type is set to the value specified in the configuration file. these control blocks are used to alter the configured command type. each block contains a command index list. the values entered in this list correspond to the indices of the commands configured by the user. the first command in the user command list has an index of 0 and the second has in index of 1. therefore, to alter the command type of commands 3 and 5, set the number of command indexes (word 1) to 2 and enter the values 3 and 5 in words 2 and 3. each block can handle up to 60 commands in the list. block 3000 and 3100 requests are used to change the commands listed in the block to the disable type (type = 0). block 3000 is used for port 0 and 3100 is used for port 1 commands. the format for the request block from the ladder logic is as follows: offset description length 0 3000 or 3100 1 1 number of command indexes 1 2 to 62 command index list 60 63-247 spare 186 the response block from the module to the processor has the following format: offset description length 0 reserved 1 1write block id 1 2 number of commands processed 1 3-248 spare 246 249 3000 or 3100 1
understanding the architecture MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 13 of 85 november 12, 2004 block 3001 and 3101 requests are used to change the commands listed in the block to the enable type (type = 1). block 3001 is used for port 0 and 3101 is used for port 1 commands. the format for the request block from the ladder logic is as follows: offset description length 0 3001 or 3101 1 1 number of command indexes 1 2 to 62 command index list 60 63-247 spare 186 the response block from the module to the processor has the following format: offset description length 0 reserved 1 1 write block id 1 2 number of commands processed 1 3-248 spare 246 249 3001 or 3101 1 block 3002 and 3102 requests are used to change the commands listed in the block to the conditional type (type = 2). block 3002 is used for port 0 and 3102 is used for port 1 commands. this type code should only be utilized for write commands. the format for the request block from the ladder logic is as follows: offset description length 0 3002 or 3102 1 1 number of command indexes 1 2 to 62 command index list 60 63-247 spare 186 the response block from the module to the processor has the following format: offset description length 0 reserved 1 1 write block id 1 2 number of commands processed 1 3-248 spare 246 249 3002 or 3102 1 2.3.2.3 warm boot block this block is sent from the controllogi x processor to the module (output image) when the module is required to perform a warm boot (software reset operation). this block is commonly sent to the module any time the configuration file is modified. this will force the module to read the new configuration information and to restart. the structure of the control block is shown below: offset description length 0 9998 1 1-247 spare 247 2.3.2.4 cold boot block block 9999 is used to perform a cold-boot operation on the module. the format of the block constructed by the processor is as follows:
MVI56-DH485 ? controllogix platform understanding the architecture dh485 interface module page 14 of 85 prosoft technology, inc. november 12, 2004 offset description length 0 9999 1 1-247 spare 247 2.4 master driver master mode of operation of the MVI56-DH485 module is responsible for issuing read or write commands to other remote devices on the dh485 network. these commands are user configured in the module via the master command list received from the configuration file. command status is returned to the processor for each individual command in the command list status data area. the location of this status block in the module's internal database is user defined. the following flow chart and associated table detail the flow of data into and out of the module. master mode driver dh485 memory configuration master command list status 3 1 2 4 5 0 3999 database addresses controllogix controller tags status status from module register data storage register data processor memory backplane interface command control command control command control step description 1 the master driver obtains configuration data fr om the configuration file on the compact flash disk in the module. this information is used by the master driver to determine the type of commands to be issued to the other nodes on the dh485 network. 2 once configured, the master driver begins transmitting read and/or write commands to the other nodes on the network. if writing data to another node, the data for the write command is obtained from the module's internal database to build the command. 3 presuming successful processing by the nod e specified in the command, a response message is received into the master driver for processing. 4 data received from the node on the network is passed into the module's internal database, assuming a read command. 5 status is returned to the controllogix proc essor for each command in the master command list.
understanding the architecture MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 15 of 85 november 12, 2004 refer to modifying the configuration data section for a complete description of the parameters required to define the virtual dh485 master port. care must be taken in constructing each command in the list for predictable operation of the module. if two commands write to the same internal database address of the module, the results will not be as desired. all commands containing invalid data will be ignored by the module. 2.5 slave driver the slave driver mode allows the MVI56-DH485 module to respond to cif and data read and write commands issued by a remote node on the dh485 network. the following flow chart and associated table detail the flow of data into and out of the module. 0 3999 database addresses controllogix controller tags slave mode driver status status from module register data storage register data processor memory dfcm module backplane interface configuration status 4 2 3 5 1 step description 1 the dh485 slave port driver receives the configur ation information from the configuration file on the compact flash disk. this information is used to configure the serial port and define the slave node characteristics. the module simulate s n-files and cif to pe rmit remote access of the database. 2 a host device, such as an allen-bradley sl c or an mmi package issues a read or write command to the module?s node address. t he port driver qualifies the message before accepting it into the module. 3 once the module accepts the command, the data is immediately transferred to or from the internal database in the module or the ci f data area. if the command is a read command, the data is read out of the database and a response message is built. if the command is a write command, the data is written directly into the database and a response message is built. 4 once the data processing has been completed in step 3, the response is issued to the originating master node. 5 counters are available in the status block t hat permit the ladder logic program to determine the level of activity of the slave driver.
MVI56-DH485 ? controllogix platform understanding the architecture dh485 interface module page 16 of 85 prosoft technology, inc. november 12, 2004 review the modifing the configuration data section for a complete list of the parameters that must be defined for a slave port. the slave driver supports the following dh485 command set: type access description cif read 485cif, peer-to-peer, read msg requests cif write 485cif, peer-to-peer, write msg requests data table read 500cpu, peer-to-peer, read msg requests data table write 500cpu, peer-to-peer, write msg requests the data table commands require the use of files. these files are emulated in the module. the user configuration of the module defines how these files are emulated in the module. two file mappings are available. the first sets the first file number and file size for each file. using this mapping, the files are set as contiguous files overlaying the database. for example, if the user sets the file size to 200 and sets the first file number as 7, the files will overlay the database as shown in the following diagram: database register n7:0 ------------> 0 n8:0 ------------> 200 n9:0 ------------> 400 n10:0 ------------> 600 n11:0 ------------> 800 n12:0 ------------> 1000 n13:0 ------------> 1200 n14:0 ------------> 1400 n15:0 ------------> 1600 n16:0 ------------> 1800 n17:0 ------------> 2000 n18:0 ------------> 2200 n19:0 ------------> 2400 n20:0 ------------> 2600 n21:0 ------------> 2800 n22:0 ------------> 3000 n23:0 ------------> 3200 n24:0 ------------> 3400 n25:0 ------------> 3600 n26:0 ------------> 3800 in addition to the fixed file emulation, the modul e also supports user defined mapping of files. with this mapping, the user defines the dat abase offset, file number, the starting element number and the length. this data is entered in the [dh485 port x maps] section of the configuration file for each port (x=0 for port 0 and 1 for port 1. the following is an example for port 0: [dh485 port 0 maps] # db_address file_number element length start 0 10 0 100 100 12 100 100 end
understanding the architecture MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 17 of 85 november 12, 2004 with the configuration displayed above, r equests for file 10 elements 0 to 99 will be associated with the module?s internal data r egisters 0 to 99 and file 12 elements 100 to 199 will be associated with the data base register s 100 to 199. the module supports up to 50 of these data mappings. when a request is made of the slave driver, the mapping defined in this override section will first be sear ched first. if the data area in t he request is found in the list, that data mapping will be utilized. if the data area in the request is not found in the list, the fixed data area mapping will be used. 2.6 cif data the module supports the common interface file (cif) of the dh485 protocol. a separate data area can be defined for each application port. this data area is divided into read and write data and is mapped into the module?s internal database. the module?s application constantly transfers the read cif data from the cif database to the module database and the write cif data from the module to the cif database. the parameters used to define the cif database are contained in the configuration file. this optional feature of the module should only be utilized if required by a remote master on the network. otherwise, the data file functions (500cpu message) instructions should be used to access and control the module?s data. the following diagram illustrates the relationship of the dh485 drivers, the cif database and the module?s database: dh485 network module database write function read function master driver write function read function slave driver cif database request response request response request response request response read database read database write database write database write cif request read cif request cif write data cif read data important: the user can configure the size of the cif read area using the cif read count parameter. the size of the cif write area is calculated using the following formula: cif write count = 244 ? cif read count. in order to clarify the direction of dat a flow, the following shows an example:
MVI56-DH485 ? controllogix platform understanding the architecture dh485 interface module page 18 of 85 prosoft technology, inc. november 12, 2004 parameter value format read register start 600 word read register count 600 word write register start 0 word write register count 600 word cif read db offset 1200 byte cif read count 144 byte cif write db offset 0 byte this configuration will imply that the data will be transferred as shown in the following diagram: as shown in the diagram, the cif area is split into the read and write areas. the cif read area always starts at an offset in the cif file, except when the cif read count is equal to 0. in this case, the cif read area will not exist. the diagram shows how the cif area should interact with the backplane read and write area in order to achieve the correct flow of data. if a write msg from a remote slc processor is sent to byte addresses 0 and 1 in the module?s cif area, the data would be copied to word address 600 in the database and would then be read to the controllogix processor. the following diagram displays four different uses and configurations of the cif data area:
understanding the architecture MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 19 of 85 november 12, 2004 internal database cif data area example # 1 0 cif read db offset: 1000 read cif data area cif read count: 244 cif write db offset: -1 243 example # 2 0 cif read db offset: -1 write cif data area cif read count: 0 cif write db offset: 1000 243 example # 3 0 cif read db offset: 1000 read cif data area 123 cif read count: 124 124 cif write db offset: 2000 write cif data area 243 example # 4 0 cif read db offset: -1 cif read count: 0 cif write db offset: -1 243 configuration parameters example 1 only uses cif read data and utilizes the maximum read data area. example 2 only uses the cif write data and utilizes the maximum write data area. example 3 uses both cif read and write data. 124 bytes of read data are used and 120 bytes of write data are used. example 4 does not use the cif data in the application. 2.7 slc interface the dh485 driver is written for peer-to-peer operation on the dh485 network. therefore, the driver can both execute commands (master role) and respond to commands (slave role). if the driver contains no commands, ladder logic is required in the other dh485 nodes in order to control or access the data in the module containing the driver. if the driver is configured with user defined commands, these commands will control or monitor data in other nodes on the network without the ladder logic requirement. the driver is developed to support both modes of operation simultaneously. the section first describes the slc configuration required for the dh485 protocol and the cabling required. following this di scussion, the section contains example ladder logic to interface with the module?s database. the ladder logic required in an slc to interface with the dh485 driver simply requires the use of the msg instruction. the dh485 driver supports two data access options. you can interface to a module containing the dh485 driver using the cif (common interface file) or normal slc data file access. use of the cif access is limited to a data area of 244 bytes and is offered for backwards compatibility to older processors and should be used only when the data access method is not available.
MVI56-DH485 ? controllogix platform understanding the architecture dh485 interface module page 20 of 85 prosoft technology, inc. november 12, 2004 the preferred method of data access to the driver is through the use of the slc data files. this access method permits full access to the data contained in the module?s internal database. 2.7.1 slc communication set up in order to use the dh485 port on the slc, channel 0 or 1 must be configured as a dh485 port. select channel configuration from the rslogix 500 software to display the following dialog box. select one of the tabs in the dialog box to select the channel to configure with the dh485 protocol. the following figure displays an example configuration for channel 1.
understanding the architecture MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 21 of 85 november 12, 2004 select the correct baud rate used on the dh485 network. next select the node address for the slc on the network. each node on the network must have a unique node address. next set the token hold factor and maximum node address for the slc. select the apply command button to apply the settings configured. if you require help setting up the channel, select the help command button on the form. after configuring the channel, download the new configuration to the slc processor. 2.7.2 ladder logic if the slc will be used to monitor and control data in the dh485 driver device, ladder logic is required. no ladder logic is required if user commands are defined in the dh485 driver module to handle all data r equirements. the examples below describe the two data access methods: cif and data file. 2.7.2.1 cif data access cif data access permits up to 244 bytes of data in the dh485 driver module to be monitored and controlled for each port. due to the extreme limit on the data size, this method should only be used if the data file access method is not offered on the monitoring and controlling device. the driver supports both read and write access to this data area. 2.7.2.1.1 read access in order to monitor data contained in the dh485 driver module, a read command message must be executed from the ladder logic. to access the cif data area in the module, select the 485cif option for the target device in the msg instruction. the following is an example rung that displays a cif method msg instruction:
MVI56-DH485 ? controllogix platform understanding the architecture dh485 interface module page 22 of 85 prosoft technology, inc. november 12, 2004 be certain to allocate a unique area in the slc?s data file area for the control block area used by the msg instruction. failure to provide this area will result in unpredictable behavior. select the setup screen area in the msg instruction to display the following dialog box: this example reads 10 words of data from the cif data file in the module starting at byte offset 0 in node 2 and places the response data in the data file n10:0 to 9. note that the data table offset value is a byte offset and not a word offset. the size of data read is determined by the number of elements times the size of each element. for a n-type file, the size is 1 word (2 bytes). for a f-type file, the size is 2 words (4- bytes). 2.7.2.1.2 write access in order to control data contained in the dh485 driver module, a write command message must be executed from the l adder logic. two hundred and fourty-four (244) bytes are available in the cif read data area (byte addresses 0 to 241). to
understanding the architecture MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 23 of 85 november 12, 2004 alter the cif data area in the module, select the 485cif option for the target device in the msg instruction. the following is an example rung that displays a cif method msg instruction: be certain to allocate a unique area in the slc?s data file area for the control block area used by the msg instruction. failure to provide this area will result in unpredictable behavior. select the setup screen area in the msg instruction to display the following dialog box: this example will place the 10 words from the slc data file n9:0 to 9 in the cif data area starting at byte offset 100 in node 2. note that the data table offset value is a byte offset and not a word offset. the size of data written is determined by the number of elements times the size of each element. for a n-type file, the size is 1 word (2 bytes). for a f-type file, the size is 2 words (4-bytes).
MVI56-DH485 ? controllogix platform understanding the architecture dh485 interface module page 24 of 85 prosoft technology, inc. november 12, 2004 2.7.2.2 data file access the data file access method permits full access to the full internal database of the dh485 driver module. this access method supports normal slc file read and write access to the data in the module. 2.7.2.2.1 read access in order to monitor data contained in the dh485 driver module, a read command message must be executed from the ladder logic. to read the data area in the module, select the 500cpu option for the target device in the msg instruction. the following is an example rung that displays a data file access method msg instruction: be certain to allocate a unique area in the slc?s data file area for the control block area used by the msg instruction. failure to provide this area will result in unpredictable behavior. select the setup screen area in the msg instruction to display the following dialog box:
understanding the architecture MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 25 of 85 november 12, 2004 this example will read 10 words from the module and place the data in the slc data file area n10:0 to 9. n-files are emulated on the module containing the dh485 driver. if the module is configured for the first n file of n7, a file size of 200 and a file offset value of 0, the module will respond with the words held in the module?s internal database registers 200 to 209 for this command. refer to the dh485 driver database documentation for a full explanation of the module?s internal database. 2.7.2.2.2 write access in order to control data contained in the dh485 driver module, a write command message must be executed from the ladder logic. to alter the data area in the module, select the 500cpu option for the target device in the msg instruction. the following is an example rung that displays a data file access method msg instruction: be certain to allocate a unique area in the slc?s data file area for the control block area used by the msg instruction. failure to provide this area will result in
MVI56-DH485 ? controllogix platform understanding the architecture dh485 interface module page 26 of 85 prosoft technology, inc. november 12, 2004 unpredictable behavior. select the setup screen area in the msg instruction to display the following dialog box: this example will write 10 words from the slc data file area n9:0 to 9 to the module. n-files are emulated on the module containing the dh485 driver. if the module is configured for the first n file of n7, a file size of 200 and a file offset value of 0, the module will place the 10 words of data received in the module?s internal database registers 200 to 209. refer to the dh485 driver database documentation for a full explanation of the module?s internal database.
module configuration MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 27 of 85 november 12, 2004 3 module configuration this section contains the setup procedure, data, and ladder logic for successful application of the MVI56-DH485 module. each step in the setup procedure is defined in order to simplify the use of the module. 3.1 setting up the module set up of the MVI56-DH485 module only requires software configuration using the rslogix 5000 program and the dh485.cfg file on the compact flash disk in the module. the easiest method to implement the module is to start with the appropriate example provided with the module mvi56dh485.acd. if you are installing this module in an existing application, you can simply copy the elements required from the example ladder logic to your application. note: this module can only be added to a project using the software in offline mode. the first step in setting up the module is to define the module to the system. right- click the mouse button on the i/o configuration option in the controller organization window to display a pop-up menu. select the new module option from the i/o configuration menu. this causes the program to display the following dialog box.
MVI56-DH485 ? controllogix platform module configuration dh485 interface module page 28 of 85 prosoft technology, inc. november 12, 2004 select the 1756-module (generic 1756 module) from the list and click the ok button. the following dialog box appears: fill in the dialog box as shown adjusting the name, description and slot options for your application. be certain to select the comm f ormat as data - int in the dialog box. failure to set the assembly instance and size values correctly will result in a module that will not communicate over the backplane of the controllogix rack. click the ok command button to display the next dialog box.
module configuration MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 29 of 85 november 12, 2004 select the request packet interval value for scanning the i/o on the module. this value represents the minimum frequency that the module will handle scheduled events. this value should not be set to less than 5 milliseconds. values between 5 and 10 milliseconds should work with most applications. after completing the module setup, the controller organization window displays the module?s presence. the data required for the module will be defined to the application, and objects will be allocated in the controller tags data area. the next step in the module?s setup is to define the user defined data types to be used with the module. copy these data types from the example ladder logic if you are not using the example. they will be defi ned if you are starting from the example ladder logic. the controller organization window should display the user defined data types shown in the following example:
MVI56-DH485 ? controllogix platform module configuration dh485 interface module page 30 of 85 prosoft technology, inc. november 12, 2004 the next step in module setup is to define the data tag to be used to interface with the module and the ladder logic. open the controller tags edit tags dialog box and enter the values shown in the following example. the MVI56-DH485 module is defined in the example as dh485_1. you can set the tag name to any valid tag name you desire. if you are using the example ladder logic, this step has already been performed. at this point, take the time to adjust array sizes for the read and write data in the dh485_1 tag. also, edit the dh485.cfg file to match the backplane data transfer parameters required for the application. add the other information to the configuration file for the specific application. use the forms in appendix b to aid in building the configuration file. the last step in the module setup is to add the ladder logic. if the example ladder logic is used, adjust the ladder to fit the application. when the ladder example is not used, copy the ladder logic shown in the controller organization window below to the application.
module configuration MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 31 of 85 november 12, 2004 the module is now set up and ready to be used with your application. insert the module in the rack and attach the dh485 serial communication cables. download the new application to the controller and places the processor in run mode. download the dh485.cfg file to the module using the configuration/debug port. if all the configuration parameters are set correctly and the module is attached to a dh485 networks, the module?s application led should remain off and the backplane activity led (bp act) should blink very rapidly. refer to the diagnostics and troubleshooting section if you encounter errors. attach a computer or terminal to the configuration/debug port on the module and check the status of the module using the resident debugger in the module. 3.2 module data object (dh485moduledef) all status and variable data related to the MVI56-DH485 is stored in a user defined data type. an instance of the data type is required before the module can be used. this is done by declaring a variable of the data type in the controller tags edit tags dialog box. the structure of the object is displayed in the following figure:
MVI56-DH485 ? controllogix platform module configuration dh485 interface module page 32 of 85 prosoft technology, inc. november 12, 2004 this object contains objects that define variables to be used with the module and status data related to the module. each of these object types is discussed in the following sections of the document. 3.2.1.1 status object (dh485instat) this object is used to store the status data of the module. the dh485instat object shown below is updated each time a read block is received by the processor. the status data for each port is passed in blocks with identification codes of 0 and ?1. this data can be used to monitor the state of the module at a "real-time rate". the structure of the dh485blkstat is shown in the following diagram and is used to store the status information for the backplane data transfer operation:
module configuration MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 33 of 85 november 12, 2004 the structure of the dh485porterrors is displayed in the following diagram: refer to appendix a for a complete list of the data stored in this object. this data is passed in blocks 0 and ?1 for each port on the module. 3.2.2 user data objects these objects are used to hold data to be transferred between the processor and the MVI56-DH485 module and to aid in the generation of the ladder logic. the user data is the read and write data transferred between the processor and the module as ?pages? of data up to 200 words long. the read data ( readdata ) is an array set to match the value entered in the read register count parameter of the dh485.cfg file. for ease of use, this array should be dimensioned as an even increment of 200 words. this data is paged up to 200 words at a time from the module to the processor. the readdata task is responsible
MVI56-DH485 ? controllogix platform module configuration dh485 interface module page 34 of 85 prosoft technology, inc. november 12, 2004 for placing the data received into the proper position in the read data array. this data can be used for status and control in the ladder logic of the processor. the write data ( writedata ) is an array set to match the value entered in the write register count parameter of the dh485.cfg file. for ease of use, this array should be dimensioned as even increments of 200 words. this data is paged up to 200 words at a time from the processor to the module. the writedata task is responsible for placing the write data into the output image for transfer to the module. this data is passed from the processor to the module for status and control information for use in other nodes on the network. the dh485backplane object is utilized by the ladder logic to store the variables used in the backplane transfer operation. the structure of the object is shown in the following diagram: other data objects can be added to the dh485moduledef object as required for specific applications. it is recommended to only add objects or members to the dh485moduledef object that relate to the module.
modifying the sample ladder logic MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 35 of 85 november 12, 2004 4 modifying the sample ladder logic ladder logic is required for application of the MVI56-DH485 module. tasks that must be handled by the ladder logic are module read data initialization (optional), data transfer, special block handling, and status data receipt. additionally, a power-up handler should be written to handle the initialization of the module's data and to clear any processor fault conditions. the controller organization window for the example ladder logic is shown in the following window: 4.1 power up the powerup ladder logic is used to initialize the data objects used by the mvi56- dh485 module and to recover controller faults on the initial power-up of the processor. the ladder logic required to perform these tasks is shown in the following rungs.
MVI56-DH485 ? controllogix platform modifying the sample ladder logic dh485 interface module page 36 of 85 prosoft technology, inc. november 12, 2004 this rung is used to recover from a processor fault condition due to power-loss and restart when the processor is in run mode. you may also have to handle other fault conditions. additionally, a fault handler can be written for the processor to handle other faults. the mjfaults object must be defined in the controller tags before it can be used in this logic. this rung is used to initialize the last read and write values, the output image for the MVI56-DH485 module and the write data area to zero. the last read ( dh485_1.bp.lastread ) and write ( dh485_1.bp.lastwrite ) values are used in the data transfer logic. the output image for the MVI56-DH485 module ( local:1:o.data[] ) is used to transfer data from the processor to the module. the write data area ( dh485_1.writedata[] ) is used to store the processor data to be written to the module using the output image. 4.2 mainroutine the mainroutine is used to recognize the presence of new read data from the module for the processor. the module will cycle through its list of read blocks to transfer data from the module to the processor. whenever new data is available, the module will set the value for the block in the module's input image ( local:1:i:data[249] ). the ladder logic must constantly scan this input word for a new value. when a new value is present, the ladder logic should perform the readdata and writedata tasks in that order.
modifying the sample ladder logic MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 37 of 85 november 12, 2004 4.3 readdata the readdata task is responsible for handling all new data received from the module and placing it in the proper location in the processor. data is transferred from the module to the processor using the module's input image ( local:1:i:data[] ). the first rung of the task sets the last read block number ( dh485_1.bp.lastread ) to the current block number sent from the module ( local:1:i:data[249] ). the module will send block identification code 0 (and possibly ?1 if not configured for any read blocks) to the processor. these blocks will only contain the status data. the following rung shown displays logic to handle these blocks: the last rung of the ladder logic determines if the new data received in the input image is user data. if user data is present, the ladder logic will place the data in the correct location in the processor's read data area ( dh485_1.readdata[] ). up to 200 data words can be transferred in each block transfer. in addition to the user data, the block also contains general status data. this data should be copied to the correct data area in the module ( dh485_1.instat ). this status data can be used to determine the "health" of the MVI56-DH485 module.
MVI56-DH485 ? controllogix platform modifying the sample ladder logic dh485 interface module page 38 of 85 prosoft technology, inc. november 12, 2004 4.4 writedata the writedata task is responsible for sending data from the processor to the mvi56- dh485 module and for build control blocks. data is transferred from the processor to the module using the module's output image ( local:1:o:data[] ). the first rung is used to store the currently requested data set in the module's dh485_1.bp.lastwrite data object. this object is used in all subsequent ladder logic in case the input word ( local:1:i:data[1] ) changes during processing. the next two rungs are used to handle processor control of the module using the warm- and cold- boot control block numbers. when the processor requires the module to perform one of these operations, it simply copies the block number into the output image of the module and the module will perform the operation. be certain to set the required block number in the last write object to prevent further processing in the writedata task. examples of each control block is given below:
modifying the sample ladder logic MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 39 of 85 november 12, 2004 the next rung displays an example of command control using block identification code 3000 to disable commands in the command list. the following example rung will disable one command (command index 0).
MVI56-DH485 ? controllogix platform modifying the sample ladder logic dh485 interface module page 40 of 85 prosoft technology, inc. november 12, 2004 the next rung displays an example of command control using block identification code 3001 to enable commands in the command list. the following example rung will enable one command (command index 0). if the module is configured for no or only one block transfer, special processing is required. the module must observe the first word of the module's output image changing in order to recognize the receipt of new data. if the value never changes, the module will not process the data. this presents a problem when fewer than two blocks are to be transferred to the module from the processor. to overcome this problem, the module will send -1 and 0 in the input word. when the module is configured for zero write blocks, the following block request sequence will be present: -1, 0, -1, 0... when the module is configured for one write block, the following block request sequence will be present: 1, 0, 1, 0, 1, 0... the rung below is required to handle these conditions. the next rung in the ladder logic is the most important. it handles the transfer of processor data to the module. up to 200 words of user data held in the processor ( dh485_1.writedata[] ) can be transferred to the module at one time.
modifying the sample ladder logic MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 41 of 85 november 12, 2004 if the module is configured to use the optional initialization of the read data area, ladder logic is required. the following rung demonstrates how to process these request blocks from the module: this option is used to initialize the read data of the module to a known state before the module starts the normal data transfer between the module and the processor.
MVI56-DH485 ? controllogix platform modifying the sample ladder logic dh485 interface module page 42 of 85 prosoft technology, inc. november 12, 2004
modifying the configuration data MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 43 of 85 november 12, 2004 5 modifying the configuration data in order for the module to operate, a configuration file (dh485.cfg) is required. this configuration file contains information to set the data transfer characteristics between the module and the processor, to configure the module?s peer-to-peer dh485 port characteristics, file mapping and user def ined command list. each parameter in the file must be set carefully in order for the application to be implemented successfully. before editing the file, design your system using the forms located in appendix b of this document. appendix b contains a configuration form to be used to construct the dh485.cfg file. appendix c contains an example listing of a dh485.cfg file. the text file is separated into four sections with topic header names enclosed in the [ ] characters. the sections present in the file are as follows: section name descri p tion [module] module parameters and backplane configuration information. [dh485 port x] general parameters for a specific dh485 port on the module. [dh485 port x commands] commands to be generated by the specific port driver [dh485 port x maps] override file maps for the specific port driver. these maps are used when data file requests are made of the module. after each section header, the file contains a set of parameters. unique labels are used under each section to specify a parameter. each label in the file must be entered exactly as shown in the file for the parameter to be identified by the program. if the module is not considering a parameter, check the label for the data item. each parameter's value is separated from the label with the ' : ' character. this character is used by the program to delimit the position in the data record where to start reading data. all data for a parameter must be placed after the ' : ' character. for numeric parameter values any text located after the value will not be used. there must be at least one space character between the end of the parameter value and the following text. an example of a parameter entry is given below: error/status offset : 3000 #database location for error/status data the parameter label is "error/status offset" and the parameter value is 3000. the characters after the parameter value are ignored and are used for internal documentation of the configuration file. any record that begins with the ' # ' character is considered to be a comment record. these records can be placed anywhere in the file as long as the ' #' character is found in the first column of the line. these lines are ignored in the file and can be used to provide documentation within the configuration file. liberal use of comments within the file can ease the use and interpretation of the data in the file. the command list and file mapping definition sections are formatted differently than the other sections. these sections contain lists of parameters to be used. each list begins with the label start and ends when the end label is reached. when
MVI56-DH485 ? controllogix platform modifying the configuration data dh485 interface module page 44 of 85 prosoft technology, inc. november 12, 2004 entering the records into the list, make certain that the first character in each line is left blank. the [dh485 port x commands] section for each port is used to define the commands to be issued by the module to other devices on the network. these commands can be used for data collection and/or control. 5.1 command list overview in order to interface the MVI56-DH485 module to act as a master device, the user must construct a command list for each port. the commands in the list specify the node to be addressed, the function to be performed (read or write), the data area in the device to interface with and the registers in the internal database to be associated with the device data. the command list supports up to 100 commands. the command list is processed from top (command #0) to bottom. a poll interval parameter is associated with each command to specify a minimum delay time in seconds between the issuance of a command. if the user specifies a value of 10 for the parameter, the command will be executed no more frequently than every 10 seconds. write commands have a special feature, as they can be set to execute only if the data in the write command changes. if the register data values in the command have not changed since the command was last issued, the command will not be executed. if the data in the command has changed since the command was last issued, the command will be executed. use of this feature can lighten the load on the network. in order to implement this feature; set the enable code for the command to a value of 2. 5.1.1 command entry format each command entered in the command list section has the same format. the following is an example section for port 0: [dh485 port 0 commands] command list for first dh485 port # swap codes : 0=none, 1=swap words, 2=swap bytes and words, 3=swap bytes # filetype codes : 0=status, 1=bit, 2=timer, 3=counter, 4=control, 5=int, 6=float, 10=cif # enablecode db_address count swap poll_int node func filetype file# element# start 1 1000 10 0 0 1 1 5 10 0 1 1010 10 0 0 1 0 5 11 0 end the first part of each record in the section relates to the module interface and the last part relates to the node to be interfaced with. the following table details the definition of each field required for a user command: field definition enable type code this field defines if the command is enabled and when it should be executed. the following codes are recognized by the application: 0 = command is disabled 1 = command is executed at the polling interval specified 2 = the write command is only executed when data changes
modifying the configuration data MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 45 of 85 november 12, 2004 field definition database start address this field defines the starting address in the module's internal database to associate with the command. this field can have a value from 0 to 3999. the address supplied is a word address in the database. element count this field defines the number of elements to be used with the command. if the command is interfacing with cif dat a, this parameter represents a byte count. for data file access, the data si ze utilized is dependent on the file type used. swap code this field is used to change the order of the bytes and/or words used when sending or receiving the data. the following codes are utilized: 0 = no data swapping 1 = swap words in the data buffer 2 = swap words and bytes in the data buffer 3 = swap bytes in the data buffer poll interval this field is used to set the time interval between successive execution of the command. this parameter is specified in seconds. if the field is set to 10, the command will not be executed more frequently than every 10 seconds. node number this field is used to define the nod e address of the dh485 node to send the command request. this field should be set to a value from 0 to 31. function code this field defines the function to be executed by the command. the module uses the following codes: 0 = read 1 = write file type this field is used to define the file ty pe to be interfaced with in the other dh485 node. the program utilizes the following codes for this field: 0 = status file (2 bytes per element) 1 = bit file (2 bytes per element) 2 = timer file (6 bytes per element) 3 = counter file (6 bytes per element) 4 = control file (6 bytes per element) 5 = integer file (2 bytes per element) 6 = floating-point file (4 bytes per element) 10 = cif file (1 byte per element) file number this field defines the file number to a ccess. this field is ignored for cif file access and should be set to 0. for bit, timer, counter, control, integer, and float data types, a maximum value of 255 is valid. element number this field defines the first element in the file specified to be associated with the command. for a cif file, this parameter is given as the byte location. for bit, timer, counter, control, integer, and float data types, the maximum value is 255. for cif data types the maximum value is 510. the maximum number of elements requested from a remote node is determined by the file type and function code utilized in the command. the following table lists the maximum element count for each file type:
MVI56-DH485 ? controllogix platform modifying the configuration data dh485 interface module page 46 of 85 prosoft technology, inc. november 12, 2004 maximum element counts for read/write commands file type bytes/ elements read result write result status 2 83 83 bit 2 118 115 timer 6 39 38 counter 6 39 38 control 6 39 38 integer 2 118 115 float 4 59 57 cif 1 236 234 5.2 file override mapping the [dh485 port x maps] section for each port is used to define file override mappings for the module. use of these maps provides flexibility defining the file emulation supported in the slave driver of the module. up to 50 maps can be defined in the module to override the fixed file-mapping feature of the module. 5.2.1 file override entry format each file map entered in the configuration file has the same format. the following is an example section for port 0: [dh485 port 0 maps] override file maps for first dh485 port # db_address file_number element length start 0 10 0 100 100 12 0 100 end the following table details the definition of each field required for an override map: field definition database start address this field defines the starting address in the module's database for the file emulation. this parameter can be assigned a value of 0 to 3999. file number this field defines the file number to be emulated at the database location specified. element this field specifies the first element in the file to be emulated. this element number corresponds to the database start address set for the record. word count (length) this field defines the number of word registers to be emulated in the file. these file maps are searched first when a node on the network makes a request. if the requested data area is found in the map list, the database area associated with the command will be utilized. if the requested data area is not found in the map list, the fixed mapping data configuration will be used.
diagnostics and troubleshooting MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 47 of 85 november 12, 2004 6 diagnostics and troubleshooting the module provides diagnostic information in three forms to the user. 1) status data values are transferred from the module to the controllogix processor. 2) all data contained in the module can be viewed through the configuration/debug port to an attached terminal emulator. 3) led status indicators on the front of the module yield information on the modules status. the following sections explain how to obtain the status data from the module and the meaning of the individual led's on the module. 6.1 status data from the module?s input image the MVI56-DH485 module returns a 15-word status data area in each normal read block (input image) that can be used to determine the module?s operating status. this data is transferred to the controllogix processor continuously. on each cycle of data transfer to the processor, the modul e will pass block 0 and/or ?1. these blocks contain the status data for each port and the general module status data. for a complete listing of the status data object, refer to appendix a. 6.2 configuration/debug port the module contains a configuration/debug port that is used to transfer the configuration between the module and a remote pc and to view all the configuration and status data of the module. the sections below discuss the facilities offered on this interface. 6.2.1 required hardware the hardware requirements to interface with the configuration/debugger port are not too stringent. a personal computer with a standard serial port should suffice. for optimal performance, the minimum is required: ? 80468 based processor (pentium preferred) ? 1 megabyte of memory ? at least one serial communications port available additionally, a null-modem cable is r equired between your pc and the port. the module's port has a db-9 male connector at the end of a rj-45 to db-9 pigtail. the rj-45 end of the cable is to be placed in the MVI56-DH485 port 1 connector (top port). the cable required is displayed in the following diagram:
MVI56-DH485 ? controllogix platform diagnostics and troubleshooting dh485 interface module page 48 of 85 prosoft technology, inc. november 12, 2004 2 3 5 rxd txd com MVI56-DH485 configuration/debug port cable db-9 male rxd txd com rs-232 host 6.2.2 required software the software required on your personal computer to interface with the configuration/debugger port is operating system dependent. tested software includes the following: dos procomm, ps-term and several ot her terminal emulation programs windows 3.1 terminal windows 95/98 hyperterminal and ps-term windows nt/2000/xp hyperterminal linux minicom any ascii terminal emulation software pa ckage provided with your operating system should work as long as it can be configured as follows: baud rate 57,600 parity none data bits 8 stop bits 1 file transfer protocol zmodem 6.2.3 using the port the following steps are required to interface with the configuration/debugger port: 1. connect your computer to the m odule's port using a null-modem cable. 2. start the terminal emulation program on your computer and configure the communication parameters to those shown in the required software section (57,600, n, 8, 1). 3. enter the '?' character on your computer. if everything is set up correctly, the port's menu will be displayed. if there is no response from the module, check the communication setup and the cable. in addition, make sure you are connected to the correct port on your computer and the module.
diagnostics and troubleshooting MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 49 of 85 november 12, 2004 6.2.4 menu options features available through the use of the configuration/debug port on the mvi56- dh485 module are all reached using single keystrokes on your computer. there is a single main menu and several sub-menus presented on the port. to view the current selections available, press the '?' key on your computer. if you are in main menu mode, the following menu will be displayed: if this menu is not displayed, press the 'm' key to display the main menu. all facilities offered by the configuration/debugger are shown on the main menu. each option is discussed below: special characters used in the display are as follows: b = block transfer statistics this menu option is used to display the configuration and statistics of the backplane data transfer operations. after selecting this option, the following will be displayed. selecting this option at one-second intervals can be used to determine the number of blocks transferred each second. c = module configuration this option displays the general module configuration information for the mvi56- dh485 module. after selecting the option, the following screen will be displayed:
MVI56-DH485 ? controllogix platform diagnostics and troubleshooting dh485 interface module page 50 of 85 prosoft technology, inc. november 12, 2004 d = database view selection of this menu option places the program in database view menu mode. this mode of operation is used to display the module's internal database values. to view the menu options available in this mode, press the '?' key and the following menu will be displayed: all data contained in the module's database is available for viewing using the menu options. each option available on the menu is discussed in the sections below: 0-3 = register pages 0-3000 this menu option is used to jump to a specific set of registers in the database and display the data. the keys perform the following functions: key function 0 display registers 0 to 99 1 display registers 1000 to 1099 2 display registers 2000 to 2099 3 display registers 3000 to 3099 s = show again this menu option is used to display the current page of 100 registers in the database. example output of the database display is shown below: - = back 5 pages this menu option is used to skip the previous 500 registers of data for viewing and display the data. p = previous page
diagnostics and troubleshooting MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 51 of 85 november 12, 2004 this menu option is used to select and display the previous 100 registers of data. + = skip 5 pages this menu option is used to skip 500 registers of data and to display the new page of data. n = next page this menu option is used to select the next 100 registers of data for viewing and displays the data. d = decimal display this menu option is used to display the data on the current page in decimal format. h = hexadecimal display this menu option is used to display the data on the current page in hexadecimal format. f = float display this menu option is used to display the data on the current page in floating-point format. the program assumes that the values are aligned on even register boundaries. if floating-point values are not aligned as such, they will not be displayed properly. a = ascii display this menu option is used to display the data on the current page in ascii format. this is useful for regions of the database that contain ascii data. m = main menu this menu option is used to return to the main menu mode. 6.2.4.1 e and f = dh485 port x menu these menu options are used to view the configuration and status data related to the dh485 driver for each of the application ports. after selecting one of the menu options, press the ? ? ? key to display the following menu: select one of the options from the menu to perform one of the operations available on the menu. each menu option is discussed in the following sections:
MVI56-DH485 ? controllogix platform diagnostics and troubleshooting dh485 interface module page 52 of 85 prosoft technology, inc. november 12, 2004 c = configuration this menu option is selected to view the configuration information for the dh485 port. after selecting the option, the following will be displayed: e = command error list this menu option is selected to view the command error list for the user-defined commands. select the ? ? ? key to view the following menu: the following is an example command error list display: l = command list this menu option is selected to view the user-defined commands for the port. select the ? ? ? key to view the following menu: the following is an example command list display:
diagnostics and troubleshooting MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 53 of 85 november 12, 2004 o = override file map list this menu option is selected to view the user defined file map configuration data. after selecting the option, press the ? ? ? key to view the following menu: the following is an example override file map list display: s = status data this menu option is selected to view the status data for the dh485 port. after selecting the option, the following will be displayed: the cfg error: parameter displayed will have a value of 0x0000 if there are no configuration errors for the driver. this is a bit mapped value (displayed in hexadecimal format) with each bit representing a configuration error. the following table lists the bits used by the module:
MVI56-DH485 ? controllogix platform diagnostics and troubleshooting dh485 interface module page 54 of 85 prosoft technology, inc. november 12, 2004 bit code description 0 0x0001 invalid baud rate 1 0x0002 invalid node address 2 0x0004 invalid maximum node address 3 0x0008 invalid token hold facto r 4 0x0010 invalid response timeout 5 0x0020 invalid status or command error db offset 6 0x0040 invalid cif read count or db offset 7 0x0080 invalid cif write db offset 8 0x0100 invalid file size 9 0x0200 invalid file offset 10 0x0400 11 0x0800 12 0x1000 13 0x2000 14 0x4000 15 0x8000 v = version information this menu option is selected to the version information for the dh485 driver. after selecting the option, the following will be displayed: m = return to main menu this menu option is selected to return to the main program menu. r = transfer configuration from pc to mvi unit this menu option is selected to transfer a new dh485.cfg from a remote pc to the module. this operation is required when the changes in the configuration of the module are made. after selecting the option, follow the instructions displayed on the terminal. the zmodem protocol is required to transfer the file from the pc to the module. the name of the configuration file must be dh485.cfg. after the download process succeeds, the module will perform a warm boot operation to implement the new configuration. s = transfer configuration from mvi unit to pc this menu option is used to transfer the configuration file present on the module?s compact flash disk to a remote pc. after selecting the option, follow the instructions presented on the terminal. the zmodem file-transfer protocol is required for this operation. v = version information this option is used to view the current version of the software for the module and other important values. after selecting the option, the following will be displayed:
diagnostics and troubleshooting MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 55 of 85 november 12, 2004 this information may be requested when calling for technical support on the product. values at the bottom of the display are important in determining module operation. the program scan counter value is incremented each time a module's program cycle is complete. this value can be used to determine the frequency of program execution by pressing the 'v' key at one-second intervals. w = warm boot module this option is selected when a warm-boot operation is required of the module. this request is automatically made after a new configuration file is downloaded to the module. this operation can be performed to initialize the database and all module status data. esc = exit program this option is used to exit the program and perform a reboot of the module. this option should only be selected if instructed by the prosoft technical support group. if you select the option, the module will cease operation. data will no longer be transferred between the ports and the module and between the controllogix processor and the module. this might cause an upset to a currently running process. 6.3 led status indicators the led's indicate the module?s operating status as follows:
MVI56-DH485 ? controllogix platform diagnostics and troubleshooting dh485 interface module page 56 of 85 prosoft technology, inc. november 12, 2004 prosoft module color status indication on data is being transferred between the module and a remote terminal using the configuration/debug port. p1 green off no data is being transferred on the configurat ion/debug port. on data is being transferred between the module and the dh485 network on port 0. p2 green off no data is being transferred on the port. on data is being transferred between the module and the dh485 network on port 1. p3 green off no data is being transferred on the port. off the MVI56-DH485 is working normally. app amber on the MVI56-DH485 module program has recognized a communication error. on the led is on when the module is performing a write operation on the backplane. bp act amber off the led is off when the module is performing a read operation on the backplane. under normal oper ation, the led should blink rapidly on and off. off the card is not receiving any power and is not securely plugged into the rack. green the module is operating normally. ok red/ green red the program has detected an error or is being configured. if the led remains red for over 10 seconds, the program has probably halted. remove the card from the rack and re-insert the card to restart the module's program. off the battery voltage is ok and functioning. bat red on the battery voltage is low or the battery is not present. replace the battery on the module. during module configuration, the ok will be red and the app and bp act led?s are on. if the app, bp act and ok led?s blink at a rate of every one-second, call prosoft technology, inc. support. there is a serious problem with the module, and it may have to be sent back to prosoft. 6.3.1 clearing a fault condition typically, if the ok led on the front of the module becomes illuminated red for over ten seconds, a hardware problem has been det ected in the module or the program has exited. to attempt to clear the condition: 1. remove the card from the rack and re-insert the card in the rack. 2. verify the configuration data being transferred to the module from the controllogix processor. if the module?s ok led does not turn green, make sure the module is inserted completely into the rack. if this does not cure the problem, contact the factory.
diagnostics and troubleshooting MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 57 of 85 november 12, 2004 6.3.2 troubleshooting the following table is designed to assist you in troubleshooting the module. please use this table to attempt to correct a problem. however, if you have additional questions or problems, please do not hesitate to contact us. the entries in this section have been placed in the order in which the problems would most likely occur after powering up the module. problem description steps to take processor fault be sure that the module is plu gged into the slot that has been configured for the MVI56-DH485 module. assure that the slot in the rack c onfiguration has been set up correctly: processor i/o led flashes this indicates there is a problem with backplane communications. be certain this and all modules in the rack are configured in the processor. bp act led remains off or blinks slowly this indicates that backplane transfe r operations are failing. use the configuration/debug port facility to check this. to establish backplane communications make su re of the following: the backplane driver is loaded in the module. the module is configured for read and write block data transfer. the ladder logic handles all read and write block situations. the module is configur ed in the processor. ok led remains red the program has halted or a critical error has occurred. connect to the configuration/debug port to see if the module is running. if the program has halted, remove the card from the rack and re-insert the card in the rack.
MVI56-DH485 ? controllogix platform diagnostics and troubleshooting dh485 interface module page 58 of 85 prosoft technology, inc. november 12, 2004
cable connections MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 59 of 85 november 12, 2004 7 cable connections the MVI56-DH485 module has the following communication connections on the module: ? two dh485 communication port (rj45 connector) ? one rs-232 configuration/debug port (rj45 connector) communication p1 p2 p3 app bp ok bat module configuration/ debug port dh485 master/slave serial port 0 dh485 master/slave serial port 1 7.1 dh485 communication ports this section describes the different methods to connect a dh485 driver enabled device to a dh485 network. the allen-bradley aic+ advanced interface converter user manual (catalog number 1761-net-aic) should be consulted for cabling requirements and configurations for a dh485 network using an aic+. the mvi56- dh485 module has two physical dh485 connectors with a rj45 plug located on the front of the module. 7.1.1 connecting the cable to the connector prosoft provides a single rj45 to male db-9 adapter to permit simpler interfacing to other devices for each port. the module's dh485 ports can be configured to operate in rs-232 or rs-485 mode. the interface to be associated with each port is set with jumpers on the module. the following sections describe each interface.
MVI56-DH485 ? controllogix platform cable connections dh485 interface module page 60 of 85 prosoft technology, inc. november 12, 2004 7.1.1.1 rs-232 when the rs-232 interface is selected, the port can be connected to a dh485 network using an aic+. the cable required for this connection is shown in the following display: 2 3 5 rxd txd com MVI56-DH485 port rs-232 cable db-9 male rxd txd com aic+ db9 port 1 3 2 5 7.1.1.2 rs-485 when the rs-485 interface is used, a single two or three wire cable is required. the use of the ground is optional and dependent on the rs-485 network. the cable required for this interface is shown in the following diagram: 1 8 5 txd/rxd+ txd/rxd- gnd MVI56-DH485 df1 port rs-485 db-9 male txd/rxd- txd/rxd+ gnd rs-485 device when connecting to port 3 of an aic+ module, the following is the correct wiring: 1 8 5 txd/rxd+ txd/rxd- com MVI56-DH485 port rs-485 db-9 male a b aic+ port 3 rs-485 4 5 3 when connecting to a 1747-aic module, the following is the correct wiring: 1 8 5 txd/rxd+ txd/rxd- com MVI56-DH485 port rs-485 db-9 male a b 1747-aic rs-485 4 5 3 an example dh485 network is disp layed in the following diagram:
cable connections MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 61 of 85 november 12, 2004 1 2 3 4 5 6 chassis gnd shield common b a termination aic+ 1 8 5 MVI56-DH485 port rs-485 db-9 male 1 2 3 4 5 6 aic+ 1 2 3 4 5 6 1747-aic to slc 5/03 channel 1 port 2 port 1 to MVI56-DH485 rs-232 to micrologix 1000 to MVI56-DH485 rs-232 1747-pic workstation this network displays the two different methods to configure the module for a dh485 network. please note there is no place on the module?s rs-485 to land the shield, and when used in the configuration shown, it must be wired externally. make certain the rs interface jumper on the module is set to the correct position: rs-232 or rs- 485. 7.1.1.2.1 jumper configurations changing from rs-232 to rs-485 requires that you change the jumper on the module to the appropriate settings. to do so, use a pair of needle-nose pliers to move the jumper shunt to the appropriate pins as shown in the following diagram:
MVI56-DH485 ? controllogix platform cable connections dh485 interface module page 62 of 85 prosoft technology, inc. november 12, 2004 note: the rs-422 jumper setting shown in the diagram is not used with this module configuration. 7.2 rs-232 configuration/debug port this port is physically an rj-45 connection. an rj-45 to db-9 pigtail cable is shipped with the module. this port permits a pc based terminal emulation program to view configuration and status data in the module and to control the module. the cable for communications on this port is shown in the following diagram: 2 3 5 rxd txd com MVI56-DH485 configuration/debug port cable db-9 male rxd txd com rs-232 host
appendix a ? MVI56-DH485 status data MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 63 of 85 november 12, 2004 appendix a ? MVI56-DH485 status data this appendix contains a listing status data presented to the processor by the module. the following table lists the data returned with each normal read block: word# byte# description 202 scan counter 203-204 product name (ascii) 205-206 revision (ascii) 207-208 operating system revision (ascii) 209-210 production run number (ascii) 211 read block count 212 write block count 213 parse block count 214 reserved 215 reserved 216 number of block errors the user can also copy this data block to the module using the error/status pointer parameter in the configuration file. the following table lists the status data passed from the module to the controllogix processor in blocks 0 and ?1:
MVI56-DH485 ? controllogix platform appendix a ? MVI56-DH485 status data dh485 interface module page 64 of 85 prosoft technology, inc. november 12, 2004 word# byte# description 2-3 0-3 active node bits for stations 0 to 31 4 4-5 online status (0=offline, 1=online) 5 6-7 node address of the unit/port emulated 6 8-9 current command index being issued 7 10-11 total number of request messages 8 12-13 total number of response messages received 9 14-15 total number of command list errors 10 16-17 configuration error word. each bit represent a configuration error condition. 11 18-19 reserved for future use. 12 20-21 total number of packets received 13 22-23 total number of packets transmitted 14 24 total retry count 25 retry failure counter 15 26 total number of nak's because of no memory for reception 27 total number of nak's because of no memory for transmission 16 28 total number of bad packets 29 total number of bad control packets 17 30 total number of packets received with a bad crc value 31 total number of parity errors 18 32 total number of framing errors 33 total number of overrun errors 19 34 total number of unexpected bytes received 35 total number of bad lsap's received 20-51 reserved for future use. 52-53 0-3 active node bits for stations 0 to 31 54 4-5 online status (0=offline, 1=online) 55 6-7 node address of the unit/port emulated 56 8-9 current command index being issued 57 10-11 total number of request messages 58 12-13 total number of response messages received 59 14-15 total number of command list errors 60 16-17 configuration error word. each bit represent a configuration error condition. 61 18-19 reserved for future use. 62 20-21 total number of packets received 63 22-23 total number of packets transmitted 64 24 total retry count 25 retry failure counter 65 26 total number of nak's because of no memory for reception 27 total number of nak's because of no memory for transmission 66 28 total number of bad packets 29 total number of bad control packets 67 30 total number of packets received with a bad crc value 31 total number of parity errors 68 32 total number of framing errors 33 total number of overrun errors 69 34 total number of unexpected bytes received 35 total number of bad lsap's received 102-201 reserved for future use. 202 scan counter 203-204 product name (ascii) 205-206 revision (ascii) 207-208 operating system revision (ascii) 209-210 production run number (ascii) 211 read block count 212 write block count 213 parse block count 214 reserved 215 reserved 216 number of block errors port 0 port 1 the data in words 10 and 60 (configuration error word) are bit-mapped values with the following definition:
appendix a ? MVI56-DH485 status data MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 65 of 85 november 12, 2004 bit code description 0 0x0001 invalid baud rate 1 0x0002 invalid node address 2 0x0004 invalid maximum node address 3 0x0008 invalid token hold facto r 4 0x0010 invalid response timeout 5 0x0020 invalid status or command error db offset 6 0x0040 invalid cif read count or db offset 7 0x0080 invalid cif write db offset 8 0x0100 invalid file size 9 0x0200 invalid file offset 10 0x0400 11 0x0800 12 0x1000 13 0x2000 14 0x4000 15 0x8000 when no configuration errors are present, the words will have a value of 0x0000 (hexadecimal). configuration errors should be corrected to have the module perform as required by the application. additionally, each command in the user command list contains an error status data area. this data can be viewed through the debug/configuration port. this data can be configured to be placed in the module?s database with each register containing an error value for each command for each port as shown in the following diagram: word# description 0 error code for command index 0. 1 error code for command index 1. --- --- 99 error code for command index 99. the error codes placed in this data area have the following definitions: dh485 general error codes error # description 0 operation successful 1 invalid parameter 2 device is already open 3 device is not present 4 invalid access 5 the function has timed out 6 7 unable to configure the requested port 8 unable to allocate memory for dh485 driver
MVI56-DH485 ? controllogix platform appendix a ? MVI56-DH485 status data dh485 interface module page 66 of 85 prosoft technology, inc. november 12, 2004 dh485 api specific error codes error # description 0x0800 command only permitted in master mode 0x0801 command already active on the port 0x0802 response to request timed out 0x0803 unable to allocate memory for the request 0x0804 illegal command or format 0x0805 host could not complete request (hardware fault) 0x0806 out of memory, file or rung does not exist 0x0807 field has an illegal value 0x0808 not enough fields in request message 0x0809 too many fields in request message 0x080a symbol not found 0x080b symbol 0 or greater than maximum characters permitted in message 0x080c does not exist, illegal size 0x080d file wrong size, address past end of file 0x080e data or file too large (memory not available) 0x080f request too large to transmit message (size+address > max message) 0x0810 access denied 0x0811 command cannot be executed 0x0812 illegal data type information 0x0813 illegal parameter, invalid data in search or command block 0x0814 file open by another node 0x0815 program owned by another node 0x0816 unknown error returned from host 0x0817 no message active on the port
appendix b ? MVI56-DH485 configuration MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 67 of 85 november 12, 2004 appendix b ? MVI56-DH485 configuration this appendix contains a listing of the data required in the dh485.cfg file in order to configure the module. the table below lists the sections and items for each section that can be used in the module configuration file (dh485.cfg): [section]/item range description if error config. value [module] configuration header for general module information module name: up to 80 chars name of the module for use on reports. use this parameter to identify your module in your system. error/status pointer: -1 to 3955 starting register location in virtual database for the error/status table. if a value of -1 is entered, the error/status data will not be placed in the database. all other valid values determine the starting location of the data. this data area includes the module version information. please refer to appendix a for information about this data block. -1 write register start: 0 to 3999 this parameter specifies the starting register in the module where the data transferred from the processor will be placed. valid range for this parameter is 0 to 3999. 0 write register count: 0 to 4000 this parameter specifies the number of registers to transfer from the processor to the module. valid entry for this parameter is 0 to 4000. 0 read register start: 0 to 3999 this parameter specifies the starting register in the module where data will be transferred from the module to the processor. valid range for this parameter is 0 to 3999. 0 read register count: 0 to 4000 this parameter specifies the number of registers to be transferred from the module to the processor. valid entry for this parameter is 0 to 4000. 0 failure flag count: 0 to 1000 this parameter specifies the number of successive transfer errors that must occur before the communication ports are shut down. if the parameter is set to 0, the communication ports will continue to operate under all conditions. if the value is set larger than 0 (1-1000), communications will cease if the specified number of failures occur. 0
MVI56-DH485 ? controllogix platform appendix b ? MVI56-DH485 configuration dh485 interface module page 68 of 85 prosoft technology, inc. november 12, 2004 [section]/item range description if error config. value initialize output data: 0 or 1 this parameter is used to determine if the output data for the module should be initialized with values from the processor. if the value is set to 0, the output data will be initialized to 0. if the value is set to 1, the data will be initialized with data from the processor. use of this option requires associated ladder logic to pass the data from the processor to the module. 0 variable name data range description if error config. value [dh485 port x] general configuration information for the specified dh485 port on the module. baud rate: 9600 or 19200 this is the baud rate to use for the dh485 network. select one of the listed baud rates. 19200 node address: 0 to 31 this is the node address to be utilized by the dh485 driver for this port on the network. enter a value not already used on the network in the range of 0 to 31. if a value of 255 is utilized or set by the module, the port is disabled. note: all nodes on the network should be set to the lowest set of values in the range of 1 to 4). 255 maximum node address: 0 to 31 enter the maximum address that the initiator searches for before wrapping to zero. the default is 31. this parameter should be set to the maximum node address set in the dh485 network. 31 token hold factor: 1 to 4 enter the number of transmissions (plus retries) that a node holding a token can send onto the data link each time that it receives the token. enter a value between 0-31. the default is 1. 1 response timeout: 1 to 50 this parameters sets the number of 100 millisecond time intervals to wait for a response to a request from the module. if the module does not receive the response with in the time period specified, a timeout condition will be set for the command. 10
appendix b ? MVI56-DH485 configuration MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 69 of 85 november 12, 2004 [section]/item range description if error config. value status db offset: -1 and 0 to 3980 this parameter sets the location of the status data for the port in the module's internal database. if the parameter is set to -1, the data is not placed in the database. if a valid value is entered, the module's status data will be placed in the database starting at the location indicated. -1 command error db offset: -1 and 0 to 3900 this parameter sets the location of the command error list data for the port in the module's internal database. if the parameter is set to - 1, the data is not placed in the database. if a valid value is entered, the module's error list data will be placed in the database starting at the location indicated. -1 cif read db offset: -1 and 0 to 7500 (only even values) this parameter sets the starting byte location in the module's database where the cif file read will be placed. this data is passed from cif memory area to t he set location in the module's database. if this parameter is set to -1, no cif read data will be utiliz ed. when the cif read area is disabled (cif read db offset = -1) or cif read count = 0, the debug menu will show this parameter as 65535. -1 cif read count: 0 to 242 this parameters sets the number of bytes to transfer from the cif file to the database. the cif write count will be calculated as (244 - cif read count) 0 cif write db offset: -1 and 0 to 7500 (only even values) this parameter sets the starting byte location in the module's database where the cif file write data will be read from. this data is passed to the cif memory area from the set location in the module's database. if this parameter is set to -1, no cif write data will be utilized. when the cif write area is disabled (cif write db offset = -1) or cif write count = 0, the debug menu will show this para meter as 65535. -1 first file: 0 to 255 this parameter sets the file number for the first file to be emulated by the module. 0 file size: 1 to 1000 this parameter sets the word size of all the files emulated in the module. 1000 file offset: 0 to 999 this parameter sets the word offset into the module's database where the file emulation will start. 0
MVI56-DH485 ? controllogix platform appendix b ? MVI56-DH485 configuration dh485 interface module page 70 of 85 prosoft technology, inc. november 12, 2004 [section]/item range description if error config. value min command delay: 0 to 10000 this parameter sets the minimum number of milliseconds to wait before issuing each command. this parameter is utilized to keep the network from being flooded with requests from the module. 0 [dh485 port x commands] command list for specified dh485 port # swap codes : 0=none, 1=swap words, 2=swap bytes and words, 3=swap bytes # filetype codes : 0=status, 1=bit, 2=timer, 3=counter, 4=control, 5=int, 6=float, 10=cif # enablecode db_address count swap poll_int node func filetype file# element# start 1 1000 10 0 0 1 1 5 10 0 1 1010 10 0 0 1 0 5 11 0 end [dh485 port x maps] override file maps for specified dh485 port # db_address file_number element length start 0 10 0 100 100 12 0 100 end the following table lists the fields required for each command list entry: field definition enable type code this field defines if the command is enabled and when it should be executed. the following codes are recognized by the application: 0 = command is disabled 1 = command is executed at the polling interval specified 2 = the write command is only executed when data changes (the enable code only applies to write commands) database start address this field defines the starting address in the module's internal database to associate with the command. this field can have a value from 0 to 3999. the address supplied is a word address in the database.
appendix b ? MVI56-DH485 configuration MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 71 of 85 november 12, 2004 field definition element count this field defines the number of elements to be used with the command. if the command is interfacing with cif dat a, this parameter represents a byte count. for data file access, the data si ze utilized is dependent on the file type used. please refe r to the maximum elem ent counts table. swap code this field is used to change the order of the bytes and/or words used when sending or receiving the data. the following codes are utilized: 0 = no data swapping 1 = swap words in the data buffer 2 = swap words and bytes in the data buffer 3 = swap bytes in the data buffer poll interval this field is used to set the time interval between successive execution of the command. this parameter is specified in seconds. if the field is set to 10, the command will not be executed more frequently than every 10 seconds. node number this field is used to define the nod e address of the dh485 node to send the command request. this field should be set to a value from 0 to 31. function code this field defines the function to be executed by the command. the module uses the following codes: 0 = read 1 = write file type this field is used to define the file ty pe to be interfaced with in the other dh485 node. the program utilizes the following codes for this field: for further detail on timer and counter data types, see the section entitled timer and counter data types following this table. 0 = status file (2 bytes per element) 1 = bit file (2 bytes per element) 2 = timer file (6 bytes per element) 3 = counter file (6 bytes per element) 4 = control file (6 bytes per element) 5 = integer file (2 bytes per element) 6 = floating-point file (4 bytes per element) 10 = cif file (1 byte per element) file number this field defines the file number to a ccess. this field is ignored for cif file access and should be set to 0. element number this field defines the first element in the file specified to be associated with the command. maximum element counts for read/write commands file type code file type bytes/ element max read elements max write elements 0 status 2 83 83 1 bit 2 118 115 2 timer 6 39 38 3 counter 6 39 38
MVI56-DH485 ? controllogix platform appendix b ? MVI56-DH485 configuration dh485 interface module page 72 of 85 prosoft technology, inc. november 12, 2004 maximum element counts for read/write commands 4 control 6 39 38 5 integer 2 118 115 6 float 4 59 57 10 cif 1 236 234 timer, counter, and control data types timer data type the timer data type uses its 3 words (6 bytes) as described below (e.g., t4:0): word 0: bit 9 ? timebase selection bit 13 ? t4:0.dn bit 14 ? t4:0.tt bit 15 ? t4:0.en word 1: t4:0.pre word 2: t4:0.acc counter data type the counter data type uses its 3 words (6 bytes) as described below (e.g., c5:0) word 0: bit 10:ua bit 11:un bit 12:ov bit 13:dn bit 14:cd bit 15:cv word 1: c5:0.pre word 2: c5:0.acc
appendix b ? MVI56-DH485 configuration MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 73 of 85 november 12, 2004 control data type the control data type uses its three (3) words (6 bytes) as shown in the following example. for example, r6:0. word 0: bit 8: fd bit 9: in bit 10: ul bit 11: er bit 12: em bit 13: dn bit 14: eu bit 15: en word 1: r6:0.len word 2: r6:.0.pos the following is a form for setting up the command list:
MVI56-DH485 ? controllogix platform appendix b ? MVI56-DH485 configuration dh485 interface module page 74 of 85 prosoft technology, inc. november 12, 2004 dh485 command definition form enable type code database start address element count swap code poll interval node number function code file type file number element number the following table lists the fields required for each record in the [dh485 port x maps] section: field definition database start address this field defines the starting address in the module's database for the file emulation. this parameter can be assigned a value of 0 to 3999. file number this field defines the file number to be emulated at the database location specified. element this field specifies the first element in the file to be emulated. this element number corresponds to the database start address set for the record. word count (length) this field defines the number of word registers to be emulated in the file. the following is a form for setting up the override map list:
appendix b ? MVI56-DH485 configuration MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 75 of 85 november 12, 2004 file override ma p definition form database start address file number element number word count ( len g th )
MVI56-DH485 ? controllogix platform appendix b ? MVI56-DH485 configuration dh485 interface module page 76 of 85 prosoft technology, inc. november 12, 2004
appendix c ? MVI56-DH485 configuration file example MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 77 of 85 november 12, 2004 appendix c ? MVI56-DH485 configuration file example this appendix contains an example dh485.cfg file listing: # dh485.cfg # # example file for the dh485 driver. this file contains a configuration to # support a peer node on a dh485 network. it will respond to request messages # for both data file and cif access. the configuration also supports a # command list that will read and write data from another node. # # date : 02/03/2003 # location: test bench # modified: rar # # # # this section of the file describes the database setup and module level # parameters. [module] module name : MVI56-DH485 communication module test error/status pointer : 3000 read register start : 400 #starting db address where read data stored read register count : 400 #number of regs to read from module by processor write register start : 0 #starting db address where write data accessed write register count : 400 #number of regs to write to module from processor failure flag count : 0 #determines if bp failure will cause protocol to be #disabled (0=ignore, >0 = failure count to disable) initialize output data : no #read output values from controller (yes or no) # this section is used to define the communication characteristics of the # first dh485 driver port (port 0). [dh485 port 0] baud rate : 19200 #baud rate of 9600 or 19200
MVI56-DH485 ? controllogix platform appendix c ? MVI56-DH485 configuration file example dh485 interface module page 78 of 85 prosoft technology, inc. november 12, 2004 node address : 2 #my node address of 0 to 31 maximum node address : 2 #maximum node address in network (1-31) token hold factor : 1 #value from 0 to 31 for this node to hold token response timeout : 10 #response timeout in 100msec increments status db offset : 1000 #db loc for port status data (-1=ignore) command error db offset : 1100 #db loc for cmd list error data (-1=ignore) cif read db offset : 4000 #db byte loc <- cif read data (-1=ignore) cif read count : 100 #numb of bytes to read from cif data area (0-244) cif write db offset : 4100 #db byte loc -> cif write data (-1=ignore) first file : 7 #first file number to emulate in db file size : 200 #number of words in each file emulated file offset : 0 #db start address for file emulation min command delay : 50 #min number of milliseconds between commands # this section contains the list of commands to execute on the dh485 driver # port. [dh485 port 0 commands] # # enable types : 0=disable, 1=poll at interval, 2=conditional poll # swap codes : 0=none, 1=swap words, 2=swap bytes and words, 3=swap bytes # function codes : 0=read, 1=write # filetype codes : 0=status, 1=bit, 2=timer, 3=counter, 4=control, 5=int, # 6=float, 10=cif # # enbl db elem swap poll node func file file element # type address count code int # code type # number start 1 400 10 0 0 1 0 5 9 0 1 400 10 0 0 1 1 5 9 10 1 410 10 0 0 1 0 10 0 10 1 410 10 0 0 1 1 10 0 20 end # this section contains a list of file override values to overlay the database. # the list will be searched by the driver for each data request made of the # driver on the specified port. if the file:element value in the request # matches an entry in the list, the database offset assigned to the entry # will be used in conjunction with the other data in the entry to return # or set the data. [dh485 port 0 maps] # db_address file_number element length start
appendix c ? MVI56-DH485 configuration file example MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 79 of 85 november 12, 2004 0 10 0 100 100 12 0 100 end # this section is used to define the communication characteristics of the # second dh485 driver port (port 1). [dh485 port 1] baud rate : 19200 #baud rate of 9600 or 19200 node address : 3 #my node address of 0 to 31 maximum node address : 5 #maximum node address in network (1-31) token hold factor : 1 #value from 0 to 31 for this node to hold token response timeout : 10 #response timeout in 100msec increments status db offset : 2000 #db loc for port status data (-1=ignore) command error db offset : 2100 #db loc for cmd list error data (-1=ignore) cif read db offset : -1 #db byte loc <- cif read data (-1=ignore) cif read count : 0 #numb of bytes to read from cif data area (0-244) cif write db offset : -1 #db byte loc -> cif write data (-1=ignore) first file : 10 #first file number to emulate in db file size : 100 #number of words in each file emulated file offset : 0 #db start address for file emulation min command delay : 50 #min number of milliseconds between commands # this section contains the list of commands to execute on the dh485 driver # port. [dh485 port 1 commands] # # enable types : 0=disable, 1=poll at interval, 2=conditional poll # swap codes : 0=none, 1=swap words, 2=swap bytes and words, 3=swap bytes # function codes : 0=read, 1=write # filetype codes : 0=status, 1=bit, 2=timer, 3=counter, 4=control, 5=int, # 6=float, 10=cif # # enbl db elem swap poll node func file file element # type address count code int # code type # number start end # this section contains a list of file override values to overlay the database. # the list will be searched by the driver for each data request made of the # driver on the specified port. if the file:element value in the request
MVI56-DH485 ? controllogix platform appendix c ? MVI56-DH485 configuration file example dh485 interface module page 80 of 85 prosoft technology, inc. november 12, 2004 # matches an entry in the list, the database offset assigned to the entry # will be used in conjunction with the other data in the entry to return # or set the data. [dh485 port 1 maps] # db_address file_number element length start end
appendix d ? product specifications MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 81 of 85 november 12, 2004 appendix d ? product specifications the MVI56-DH485 (dh485 communication module) allows allen-bradley controllogix i/o compatible processors to easily interface with other dh485 protocol compatible devices. compatible devices include not only allen-bradley slcs and plcs (which support the dh485 protocol), but also a wide assortment of end devices. general specifications the MVI56-DH485 module acts as a gateway between the dh485 network and the allen-bradley backplane. the data transfer from the controllogix processor is asynchronous from the actions on the dh485 network. a 4000-word register space in the module is used to exchange data between the processor and the dh485 network. some of the general specifications include: ? support for the storage and transfer of up to 4000 registers to/from the controllogix processor's controller tags ? module memory usage that is completely user definable ? two ports to emulate a dh485 master/slave device (peer-to-peer device) ? all configuration information contained in a single, user defined, text file (dh485.cfg) functional specifications the MVI56-DH485 module accepts dh485 commands from an attached dh485 master unit (i.e., slc 5/03 processor ladder logic msg instruction). the dh485 driver permits a remote master to interact with all data contained in the module. this data can be derived from other dh485 devices on the network through a master port or from the controllogix processor. the mv i56-dh485 module driver actively issues dh485 commands to other nodes on the dh485 network. one hundred, user defined commands are supported by the driver on each port. the controllogix processor can be programmed to control the activity on the port by actively selecting command type for each command directly from the ladder logic. physical this module is designed by prosoft technology and incorporates licensed technology from allen-bradley (controllogix backplane technology). ? contrologix form factor - single slot ? connections:
MVI56-DH485 ? controllogix platform appendix d ? product specifications dh485 interface module page 82 of 85 prosoft technology, inc. november 12, 2004 2? rj45 connectors for support of rs-232 or rs-485 interfaces for the dh485 interface drivers 1? rj45 rs-232 configuration tool connector controllogix interface ? operation via simple ladder logic ? complete set up and monitoring of module through rslogix 5000 software, user define configuration file and configuration/debug port ? controllogix backplane interface via i/o access ? all data related to the module is contained in a single controller tag with defined objects to ease in the monitoring and interfacing with the module hardware specifications the MVI56-DH485 module is designed by prosoft technology and incorporates licensed technology from allen-bradle y (controllogix backplane technology). ? current loads: 800 ma @ 5v (from backplane) ? operating temperature: 0 to 60 deg c (32 to 140 deg f) ? storage temperature: -40 to 85 deg c (-40 to 185 def f) ? relative humidity: 5-95% (w/o condensation) ? dh485 port connectors: two rj45 connectors (rj45 to db9 cables shipped with unit) supporting rs-232, rs-422 and rs-485 interfaces ? configuration connector: rj45 rs-232 connector (rj45 to db9 cable shipped with unit)
support, service, and warranty MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 83 of 85 november 12, 2004 support, service, and warranty technical support prosoft technology survives on its ability to provide meaningful support to its customers. should any questions or problems ar ise, please feel free to contact us at: factory/technical support prosoft technology, inc. 1675 chester avenue, second floor bakersfield, ca 93301 (661) 716-5100 (661) 716-5101 (fax) e-mail address: prosoft@prosoft-technology.com web site: http://www.prosoft-technology.com before calling for support, please prepare yourself for the call. in order to provide the best and quickest support possible, we will most likely ask for the following information (you may wish to fax it to us prior to calling): 1. product version number 2. system hierarchy 3. module configuration and contents of dh485.cfg file 4. module operation - configuration/debug status information - led patterns 5. information about the processor and data areas as viewed through rslogix 5000 and led patterns on the processor 6. details about the dh485 network an after-hours answering system (on the bakersfield number) allows pager access to one of our qualified technical and/or application support engineers at any time to answer the questions that are important to you. module service and repair the MVI56-DH485 card is an electronic product, designed and manufactured to function under somewhat adverse conditions. as with any product, through age, misapplication, or any one of many possible problems the card may require repair. when purchased from prosoft technology, the module has a one-year parts and labor warranty according to the limits specified in the warranty. replacement and/or
MVI56-DH485 ? controllogix platform support, service, and warranty dh485 interface module page 84 of 85 prosoft technology, inc. november 12, 2004 returns should be directed to the distributor from whom the product was purchased. if you need to return the card for repair, obtain an rma number from prosoft technology. please call the factory for this number and display the number prominently on the outside of the shipping carton used to return the card. general warranty policy prosoft technology, inc. (hereinafter referred to as prosoft) warrants that the product shall conform to and perform in accordance with published technical specifications and the accompanying written materials, and shall be free of defects in materials and workmanship, for the period of time herein indicated, such warranty period commencing upon receipt of the product. this warranty is limited to the repair and/or replacement, at prosoft's election, of defective or non-conforming product, and prosoft shall not be responsible for the failure of the product to perform specified functions, or any other non-conformance caused by or attributable to: (a) any misapplication or misuse of the product; (b) failure of customer to adhere to any of prosoft's specifications or instructions; (c) neglect of, abuse of, or accident to, the product; or (d) any associated or complementary equipment or software not furnished by prosoft. limited warranty service may be obtained by delivering the product to prosoft and providing proof of purchase or receipt date. customer agrees to insure the product or assume the risk of loss or damage in transit, to prepay shipping charges to prosoft, and to use the original shipping container or equivalent. contact prosoft customer service for further information. limitation of liability except as expressly provided herein, prosoft makes no warrant of any kind, expressed or implied, with respect to any equipment, parts or services provided pursuant to this agreement, including but not li mited to the implied warranties of merchant ability and fitness for a particular purpose. neither prosoft or its dealer shall be liable for any other damages, including but not limited to direct, indirect, incidental, special or consequential damages, whether in an action in contract or tort (including negligence and strict liability), such as, but not limited to, loss of anticipated profits or benefits resulting from, or ar ising out of, or in connection with the use or furnishing of equipment, parts or services hereunder or the performance, use or inability to use the same, even if prosoft or its dealer's total liability exceed the price paid for the product. where directed by state law, some of the above exclusions or limitations may not be applicable in some states. this warranty provides specific legal rights; other rights that vary from state to state may also exist. this warranty shall not be applicable to the extent that any provisions of this warranty are prohibited by any federal, state or municipal law that cannot be preempted. hardware product warranty details warranty period: prosoft warranties hardware product for a period of one (1) year.
support, service, and warranty MVI56-DH485 ? controllogix platform dh485 interface module prosoft technology, inc. page 85 of 85 november 12, 2004 warranty procedure: upon return of the hardware product prosoft will, at its option, repair or replace product at no additional charge, freight prepaid, except as set forth below. repair parts and replacement produc t will be furnished on an exchange basis and will be either reconditioned or new. all replaced product and parts become the property of prosoft. if prosoft determines that the product is not under warranty, it will, at the customer's option, repair the product using current prosoft standard rates for parts and labor, and return the product freight collect. - - - - - - - - - - - - - - - - end of m anual - - - - - - - - - - - - - - - - -

▲Up To Search▲

Price & Availability of MVI56-DH485

	To Download MVI56-DH485 Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .